- 6 minutes to read

Release Notes

Azure Logic Apps Logging and Monitoring Agent

Plug-and-play monitoring and logging for Azure Logic Apps—auto-discover workflows, track business transactions, detect failures, and resolve issues instantly without Azure Portal dependency.

Why Choose This Agent?

Traditional Azure Portal monitoring creates operational bottlenecks: scattered subscriptions, manual troubleshooting, limited visibility, no automated remediation. Nodinite delivers unified monitoring and logging across all Azure subscriptions with zero workflow changes.

Monitoring vs Logging: What's the Difference?

Feature Monitoring Logic Apps Logging Logic Apps
Purpose Health checks, availability, performance metrics Business transaction tracking, compliance, audit trails
Auto-Discovery ✅ All workflows (Consumption & Standard) N/A
Failed Runs Detection ✅ Real-time alerts with thresholds ✅ Full run history with payloads
Trigger Monitoring ✅ Failed trigger detection ✅ Trigger event logging
Payload Access ⚠️ Metadata only ✅ Full payloads via regex filters
Thresholds & Alerts ✅ Execution count, duration, action invocations N/A
Remote Actions ✅ Enable/Disable, Resubmit, Clear failures N/A
Business Data Search N/A ✅ Search by Order ID, Customer ID, Invoice #
End-to-End Correlation N/A ✅ Track across Logic Apps, BizTalk, databases
Azure Portal Required ❌ No ❌ No

Key Insight: Monitoring tracks workflow health (is it running? did it fail?). Logging captures business transactions (what order was processed? what payload was sent?). Use both for complete operational visibility.

Learn more about Logging vs Monitoring approaches – Diagnostics Logging vs Custom Logging, pros/cons, when to use each

How It Works

Learn more about Logging vs Monitoring approaches – Diagnostics Logging vs Custom Logging, pros/cons, when to use each

How It Works

graph TD subgraph "Azure Cloud" LA1[fa:fa-rocket Logic Apps
Consumption & Standard] Diag[fa:fa-chart-line Azure Diagnostics
Event Hub] LA1 --> Diag end subgraph "Nodinite Platform" Agent[fa:fa-code-commit Logic Apps Agent] Monitor[fa:fa-display Monitoring
Auto-Discovery & Health] Logging[fa:fa-hard-drive Logging
Full Payloads via Filters] Diag --> Agent Agent --> Monitor Agent --> Logging end Monitor --> |Remote Actions|LA1

The agent connects to Azure Diagnostics Event Hub—auto-discovers workflows, monitors health, captures filtered business transaction data with full payloads.

Setup: Enable Azure Diagnostics → Configure Event Hub → Install agent → Agent auto-discovers and monitors all Logic Apps (Consumption & Standard). Configure regex filters to capture full payloads for matching connectors.

What You Get

Auto-Discovery & Unified Monitoring

  • All Logic Apps across unlimited subscriptions—dev, test, prod regions in single dashboard
  • Consumption + Standard tiers—no separate configuration
  • Real-time health monitoring with configurable thresholds:
Monitor State Condition Remote Actions Available
OK Logic App enabled, runs within thresholds Disable, Edit thresholds, View details/history
Warning Too few/many executions, slow execution, excessive actions Edit thresholds
Error Logic App disabled, thresholds breached, failed runs Enable, Edit thresholds
Unavailable Workflow deleted Inactivate resource

Intelligent Logging with Payload Capture

  • Telemetry-first approach—agent retrieves metadata for all runs efficiently
  • Regex-based payload filters—connectors matching patterns automatically get full payloads via Azure REST API
  • Business transaction tracking:
    • Extract Order Numbers, Customer IDs, Invoice amounts with Search Field Expressions
    • Correlate across Logic Apps, BizTalk, databases, custom systems
    • Search by business data without Azure Portal
  • Message Types and Search Fields enable searchable business identifiers
  • Log Views provide role-based access to transaction logs

Detailed Logging configuration – Diagnostics vs Custom Logging, payload strategies, tracked properties

Proactive Failure Detection

  • Failed run monitoring—instant alerts when runs fail

  • Failed trigger detection—catch silent trigger failures (webhooks unreachable, queue access denied)

  • Failed trigger detection—catch silent trigger failures (webhooks unreachable, queue access denied)

  • Configurable threshold alerts—too few/many executions, slow execution, excessive action invocations

  • Auto-healing rules—resubmit failed runs, restart disabled workflows, trigger compensating actions

Remote Actions Without Azure Portal

  • Enable/Disable Logic Apps—toggle workflow state from Nodinite
  • Resubmit failed runs—retry with original or modified payload
  • Clear failure states—acknowledge and reset error conditions
  • View run history—complete action timeline with payloads
  • Role-based permissions—delegate actions without Azure credentials

Multi-Subscription Management

  • Unlimited subscriptions—single agent, single license
  • Monitor Views—filter by subscription, resource group, workflow
  • Centralized alerting—email, Teams, ticketing systems
  • Log Audits—track who did what, when

Feature Summary

Capability Description Key Benefits
Monitoring Logic Apps Auto-discover workflows, track run status, detect failures Real-time health across all subscriptions · Threshold-based alerts · Failed trigger detection
Logging Logic Apps Capture business transactions with full payloads Regex-filtered payload capture · Search by business data · End-to-end correlation
Managing Logic Apps Remote actions and auto-healing Enable/Disable · Resubmit · Clear failures · No Azure Portal required

Other Azure Monitoring Agents

Get Started

Step Task
1 Review Prerequisites – Azure subscription access, Event Hub setup, Service Principal/Managed Identity credentials
2 Install the Agent – Download installer, configure Azure credentials (multi-subscription supported)
3 Enable Azure Diagnostics – Stream Logic Apps events to Event Hub (Azure Portal → Diagnostic Settings)
4 Configure Message Types – Define business transaction types, create Search Field Expressions for Order IDs, Customer IDs
5 Set Up Monitoring – Create Monitor Views, configure alert thresholds, set notification channels

Common Questions

Q: Does this work with both Consumption and Standard Logic Apps?
A: Yes. Both tiers supported with auto-detection—no separate configuration.

Q: Do I need to modify my Logic App workflows?
A: No. Zero changes required. Uses Azure Diagnostics and built-in tracking.

Q: Can I monitor Logic Apps across multiple Azure subscriptions?
A: Yes. One agent monitors unlimited subscriptions with single license.

Q: How do I search logs by Order Number or Customer ID?
A: Configure Message Types and Search Field Expressions to extract business identifiers from tracked properties or payloads. Then use Log Views for searching.

Q: What happens with high-volume Logic Apps (thousands of events/hour)?
A: Event Hub buffers events asynchronously, agent processes batches efficiently. Configure retention policies and archive historical data.

Q: Can I resubmit failed runs from Nodinite?
A: Yes. Managing Logic Apps includes remote actions—resubmit with original/modified payload, enable/disable workflows, trigger manual runs.

Q: What Azure permissions does the agent need?
A: Logic App Contributor role (remote actions), Reader role (monitoring), Event Hub connection string. Details in Prerequisites.

Q: Can I track transactions end-to-end across Logic Apps and other systems?
A: Yes. Use correlation IDs and Search Fields for tracking. Example: Salesforce → Logic App → BizTalk → Database. Search by Order ID to see complete timeline. Business Process Modeling (BPM) visualizes workflows.

Q: How quickly does Nodinite detect failed runs?
A: Near real-time (1-3 minutes latency). Azure Diagnostics streams to Event Hub, agent polls continuously (default 30 seconds).

Next Steps

Prerequisites for Azure Logic Apps Agent – Confirm Azure access, Event Hub setup, credentials
Install Azure Logic Apps Agent – Download and configure multi-subscription monitoring
About Logic Apps Logging Options – Compare Diagnostics vs Custom Logging approaches